AXIS2-6091 - Handle 400-500 errors with content-type "text/html" #902
+224
−7
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Addresses an issue where non-SOAP HTTP error responses (4xx-5xx) with a "text/html" content type were not being properly handled, resulting in uninformative error messages. Now, the response body from these errors is extracted and included in the AxisFault detail, providing more context for debugging. This ensures that users receive more meaningful error information when such errors occur.
MCMicS
approved these changes
Apr 8, 2025
Contributor
MCMicS
left a comment
MCMicS
left a comment
There was a problem hiding this comment.
I only would remove the blank lines after return statements
Contributor
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addresses an issue where non-SOAP HTTP error responses (4xx-5xx)
with a "text/html" content type were not being properly handled,
resulting in uninformative error messages.
Now, the response body from these errors is extracted and included
in the AxisFault detail, providing more context for debugging.
This ensures that users receive more meaningful error information
when such errors occur.